Understanding the out-of-the-box sitemaps

This section discusses some of the features of the Member and Member Mobile sites, including:

■    The content records, iParts, and shortcuts used for searching

■    Standard pages that should not be used within iPart-based websites

■    How to modify the [OverrideLinkText] and [CartItemCount] dynamic navigation items

■    Profile pages linked from the Member site’s Directory, which uses an ASPX web page to redirect users to a navigation item based on a set of criteria

Working with the content records, iParts, and shortcuts used for searching

Three elements make search work in the sample sites:

■    The universal search content record: The sample sites use a universal search content record that is reused throughout the sites and is dynamically populated with an initial search result set based on a URL parameter value. The Search content record contains the Common Search iPart and is located in @/iMIS/ContentManagement/Search.

■    The pages that display the initial search results: The Shop and Events navigation items are linked to the Search content record. These navigation items have a unique value for the InitialArea URL parameter, which defines the result set generated when the page is first displayed (i.e. products or events).

■    The page displayed when a user clicks a result: The page displayed when a user clicks a search result link is based on the shortcuts defined from Site designer > Manage shortcuts. The following shortcuts display search result links in the sample sites:

□    ItemDetail –The ItemDetail shortcut displays the Item_Detail content record, which uses the Product Display iPart to display the item selected.

□    GiftDetail – The GiftDetail shortcut displays the Gift_Detail content record, which uses the Donation Creator iPart to display donation pages selected from search results.

□    EventDetail – The EventDetail shortcut displays the Event_Display content record, which uses the Event Display and Event Program Display iParts to display event pages selected from search results.

Modifying dynamic navigation items

The default sitemaps include variables that dynamically generate the text displayed for two navigation items. [OverrideLinkText] displays the Full Name of the logged in user by default. [CartItemCount] displays the number of items a user has added to the Cart.

If you want to add new navigation items that use these variables, or if you want to modify the existing ones, keep the following guidelines in mind:

■    Navigation areas and master pages – The variables only work in the Auxiliary and Footer navigation areas of websites using one of the Sample Site master pages (or copies of these files) or 1700.master. To specify a navigation area, edit a navigation item and in the Options section, select Auxiliary, Footer, or both from the Show in the following navigation areas options.

■    [OverrideLinkText] – You can use this variable on its own or with other text. For example, if you only enter the variable, then only the logged in user’s name is displayed as a link. However, if you enter [OverrideLinkText]’s Profile, and Bob Smith logs in, then Bob Smith’s Profile is displayed as a link.

■    [CartItemCount] – You can use this variable on its own or with other text, but we recommend that you only use it with other text. Otherwise, when no items are in the cart, nothing is displayed for this navigation item.

To change the data displayed for [OverrideLinkText]

The variable [OverrideLinkText] can display any property of the NetContact business object. You can change the property displayed by editing the ContactDetail property in your copy of one of the Sample Site themes, or in 1700.master.  

For example, instead of displaying the Full Name of the logged in user, you may want to display only their First Name. To make this change, edit the ContactDetail property to replace all instances of FullName with FirstName. The result should look like this:

public string ContactDetail

    {

        get

        {

            if (ViewState["ContactDetail"] != null)

                return (string)ViewState["ContactDetail"];

            _contact = Asi.Business.Contact.ContactController.Contact(Asi.AppContext.CurrentIdentity.UserKey,

                                                                      Asi.AppContext.CurrentContext.

                                                                          StatefulBusinessContainer);

            return _contact.FirstName != "GUEST" ? _contact.FirstName : String.Empty;

        }

        set { ViewState["ContactDetail"] = value; }

    }

Account and profile pages in the Member site’s Directory

When users select a result after searching the Member site’s Directory, or when they navigate to the account pages, the content record that displays depends on the user’s permissions. The rules that determine where a user is redirected are defined in the Party.aspx file, located by default in C:\Program Files\ASI\iMIS\Net.

You can modify the information displayed on the account and profile pages by editing the content records described below from Content designer > Manage content.